Try doing your next project in Perl, using the CPAN where appropriate, and you'll see that the standard libraries of Python, Java, Haskell, whatever are simply inadequate.
(In the end, it really depends on what you are doing. J2EE is probably fine for an web page that extracts some rows from a database. Most programming tasks are not that trivial, however, even if they should be.)
And I'll never use Perl again for anything on purpose. I'm not a Python fanboy, but I don't find your library comment right at all. In fact, the time I used Python was because I had to add functionality to an older Perl project. Rather then write in Perl I rewrote the entire thing in Python (that is; I chose to use a language I didn't know at the time, rather then write Perl again). The resulting source code was one third the size (I counted) and much much clearer with more features added. I didn't have to download anything for Python while the old Perl code was using 4 or 5 CPAN modules.
As for Java/Haskell, this is obviously not a fair comparison: Perl+CPAN vs. Java/Haskell standard libraries. If you include third party libraries for Java it should have far more code then any other language by now.
There really isn't a reason to; the script languages that have come since then have fixed Perl's problems without losing any power. The only argument Perl has left is CPAN [1], but given the amount of duplication and bad code there, CPAN isn't as big as it's made out to be. I don't know about Ruby, but I used Python not so long ago and I noticed that not only did it have libraries for everything I needed to do, aside from DB access (which I had to download) they were all included with python itself. This is very nice in big organizations where downloading anything is a huge pain.
[1] Well, ok, it also has the COBOL argument of "there is a large code base out there to be supported" but I would expect this argument to only be compelling to the same people that were attracted when COBOL used it.