in my eyes, it depends on what you want to do and how big the script will become.

E.g. if you've got a whole script suite that will work for a special web application, it might be a rather good idea to put the common used subroutines (or the like) into a module which is used by most of the scripts. Another point for a module might be configuration information for connections to database and the like (better never put such a module in a directory shared by web because of security), because it becomes much easier to maintain and change some items and as another benefit, code reusability might increase and the code might become more general.

But for - let's say - a simple guestbook or the like, I'd rather not use a module, but for a webforum like perl-monks, I'd use quite some modules.

I prefer loading modules that might be just needed in certain cases via require (and no import, because I hate namespace polluition), so it will be loaded in runtime if it is needed, unlike use, which loads it in every case.
How are other people handling this?

Best regards,
perl -le "s==*F=e=>y~\*martinF~stronat~=>s~[^\w]~~g=>chop,print"