This is how we manage it in my shop:

• Our server code (perl) and any modules which we use but modify heavily go into a source code repository. Perforce, actually... not cvs. It costs money but IMHO it is worth it. It's really not that expensive and it's excellent software, multi-platform, very scriptable.
• Standard modules which we use get loaded into a general system image which we sync out to all of our servers, along with standard binaries and non-perl libraries... even the O/S (currently SLES7).
• There is a little bit of a review process before we add libraries to that image. It's worth it. Any old idiot can slap something up on CPAN. Saying "it's safe because it's on CPAN" is kind of like saying "it must be true, I saw it on the web."

As for you, what is best really depends a lot on what you intend to do with this perl code. Where I work: we write a large business application built on apache/mod_perl and oracle. It's all centrally located and managed and load balanced. So we have to worry about a whole ton of machines, all of which fall into three categories:

• application servers
• oracle servers
• other servers (administrative machines, web proxies, etc)

So we need a way to make sure that all of our systems admin scripts make it out to all machines, and all of the code makes it out to all of the app servers. Anyway, that all means that we need a pretty heavily controlled environment so that it can be synchronized easily. Your needs may be different.