Personally I'd just use your OS's package manager for the modules
Are you suggesting the OP rely on the OS's package repository? Or suggesting the OP create packages for deployment using the OS's package manager?
If the first, generally it is a bad idea for "non system" Perl applications to use the "system Perl" as updates are more likely to cause problems. It is better to leave the system Perl for OS's use and install one or more separate versions of Perl for non system applications.
If the second, I think it would be easier (and more portable) to deploy applications by creating the same type of package CPAN uses. The resulting tar.gz file can be copied to each server and the cpan command con be used to install it:
cpan> install myapp.tar.gz
Would even be possible for the OP to setup a CPAN-like archive and direct cpan to use that before using the actual CPAN archive.