Sorry to go off here, but I think you're way off-base on some of these. I'm a member of the Apache Software Foundation, so chalk this up to bias if you like.

mod_perl

Your complaint is that you can't find a cheap enough ISP. How cheap is cheap enough? You can get a virtual server dirt cheap these days. You can run on EC2. Or, if it's mod_perl itself that you don't like and not the cost of hosting, you can run FastCGI, which is widely available on cheap ISPs. There is no ISP problem for Perl5.

Also, mod_perlite offers nothing interesting beyond mod_perl, and the idea that it will become ubiquitous on ISPs makes no sense. I've gone into the details on this before.

Perl Web Pages

I think it's pretty clear by now that there will never be one templating system to rule them all, in Perl or any other language. There are intelligent arguments to be made on both sides of the mini-language vs. in-line perl debate and quality tools available for both. Thankfully most people don't write new ones and put them on CPAN anymore, but I don't think there will ever be just one.

And it's not clear to me what you dislike about the current crop of web dev systems (reading requests, managing sessions, etc.).

Perl6 Web Server

Do you know how hard it is to write a decent HTTP server? Never mind the performance question -- just try to get all the details of HTTP and the many random clients out there correct, let alone fast, and you'll be busy for years. Then consider that web servers are one of the biggest security concerns ever, and think about how much time has been invested in securing the code in popular servers like Apache. It's not perl that's the problem here but rather the amount of work involved in getting this stuff right. Starting from scratch is a bad idea.

WSDL

Hey, we agree on something! I'm more concerned about reading WSDL than writing it, but it would certainly help. SOAP clients are far too painful in Perl right now.