Just in theory:

If your users are calling many scripts in a session you could also consider using wrappers to start the perl-binary only once.

First start would compile all scripts (as subs) and at termination go into background and "freeze".

The next wrapper-call would just need to find and "defreeze" the process and call the already compiled sub.

The drawback would be the constant memory consumption of an independent perl process per user and like in mod_perl you have to be very prudent about any side-effects of your scripts.

Update

Seems like MLX's suggestion of "persistent perl" follows more or less these ideas ... :)