I'm worried for you.
You should roll all third party modules to live servers using either precompiled packages that ship with your platform, or that you create yourself with the package management system that works on your platform. This applies to binary modules OR non-binary modules. If your platform doesn't have a package management system, you should get one. Managing more than one server without it is a bad thing. It seems that only Gentoo Linux is missing package management - but even then you should be able to install RPM management and just use it for your custom perl modules.
If your platform doesn't have a version of a module, I would suggest using cpan2rpm or cpan2deb.pl which will make, make test, and create an rpm or .deb for your code. If your platform of choice has precompiled modules already available through a yum or apt repository then you should use those first as they are already tailored to work with your other installed software. Package management tools work just fine on all of the standard unix and linux platforms.
If you are doing truly custom stuff with lots of modifications and cpan2rpm or cpan2dep won't work you you, then you should try checkinstall which will sometimes work.
On windows, you should use PPM as another poster has already said.
Production servers should have an auditable log of the software that is installed and whether there are files there that don't belong.
my @a=qw(random brilliant braindead); print $a[rand(@a)];