In some instances you can use perlcc to create a compiled version of your program, although, according to the documentation, "Use for production purposes is strongly discouraged." Experimental code and all that. It's worth a try, if you're really desperate, since it ends up being compiled code.

If this program is used on a semi-regular basis, you could always leave it running as a "daemon" process, allowing other programs to call it as required using a socket. This isn't as risky, but you should have a good example of how to make a daemon process handy, for example, from the Perl Cookbook. A cheap way of doing this is to turn it into an Apache module, where it can be accessed using HTTP.