I'm not a web guru nor a Perl one, but i have used CGI.pm a lot in the past and i still maintain a little portal using it.
I feel the need to upgrade to something modern, because there are a lot of good alternatives. But as always speacking of Perl web dev, there is a little misunderstanding.

There is the protocol and there is the implementation. I suppose that the protocol is dead as idea, but the implementation can be usable, in very short, protected env. As you have shown. I also consider it still valid as html spawner:

 
use CGI qw /:html/; 
my $q = CGI->new;

print $q->redirect( 'http://www.perlmonks.org');
[download]

Anyway there are valid reasons to consider CGI dead: look at SawyerX condamning it: CGI.pm must die! and again SawyerX in the interview where he tells about a Lincoln Stein's answer to the previous talk. As SayerX (coauthor of Dancer) said, i'm thankfull to Lincoln Stein, but we lost a lot of time and now we have to look forward: PSGI is the new protocol and Plack it's implementation.

Notice also, even if i agree with you about CGI as still good module, in the official doc of the module is stated clearly:

CGI.pm HAS BEEN REMOVED FROM THE PERL CORE

..

The rationale for this decision is that CGI.pm is no longer considered
+ good practice for developing web applications, including quick proto
+typing and small web scripts. There are far better, cleaner, quicker,
+ easier, safer, more scalable, more extensible, more modern alternati
+ves available at this point in time. These will be documented with CG
+I::Alternatives.
[download]

More on we are told to not use html generation, too...

L*