I don't, however, think that it's about functional programming. It's about flexibility: if everything is an expression, you can use any bit of code in relation to any other, and not worry about what parts of the languages are merely statements ... a JavaScript example being "var a = b", which cannot be used as part of a larger computation.
Having every function return a value is something that seems extraneous at first look, but ends up encouraging good API design. From the point of the caller of the function, returning a meaningful value is always appreciated -- even if it's as simple as returning "true" to acknowledge that the operation was completed successfully.
(Technically Ruby does have a return keyword, but it's optional. Same goes for CoffeeScript, I believe.)
But you are quite right that Perl if/else are statements and not expressions. Instead you can use the ternary operator:
my $value = $cond == 1 ? 'true' : 'false';
And because of ditto for Perl you can also do following: my $value = do { if ($cond == 1) { 'true' } else { 'false' } };
Incidentally, what's the most successful recent language that tries to make functional programming terser by not having an explicit "return" keyword (everything's an expression)? I'm genuinely curious, and don't think any significantly great number of programmers will ever find this style easier.