PAR provides a good solution here. I have successfully used it to deploy Perl code into production, in an environment hostile to open source, and to Perl by implication.

Using PAR, what I am delivering is a PAR executable, the source being a Perl script. Such an 'executable' is taken through a full development and testing cycle before being put live.

Because PAR executables include perl itself, you eliminate the dependency on perl versions. You also eliminate the module interdependency nightmare that afflicts applications that use CPAN - this is moved back to 'development', where it belongs.

Also worth mentioning is the isolation benefit that this gives you, in that each application so deployed, indeed each version thereof, is independent of every other application deployed.