To give a little more evidence. This problem used to exist for PHP as well, take a look at this post:-
http://www.phpbuilder.com/lists/php3-list/199905/1278.php

Rather than ignoreing this issue, blaming new or bad programmers (as if advanced programmers don't make mistakes from time to time), etc. The PHP people did something about it back in version 3. Take a look at the responces, such as:-
http://www.phpbuilder.com/lists/php3-list/199905/1280.php
and
http://www.phpbuilder.com/lists/php3-list/199905/1293.php

If I wasn't such an avid perl fan I might be tempted to php, but no way.

When someone uploads a script that causes an Iloop on my server I run 'top' and kill it. If it's the middle of the night my server will be running like a slug until i wake up and kill the run away scripts. I'd rather not have to do this. It's no where near the problem you get on Win32, but it's still an issue. However on Linux you could argue this is a issue with apache not killing the cgi process it started when the browser stop button is pressed. Should my next stop be apache? Either way, the simplest solution would be perl having some sort of safeguard to prevent this.