I think it depends on who are using your Perl software. If they're also developers, I think they will find no problem using CVS, and you don't need to roll your own "remote update facilities".

But if it is used by end users, I mean those who aren't familiar with programming tools such as CVS and won't bother taking time to learn using it, then it's time for you to create such thing. Admittedly, CVS is overkill for this purpose.

I remember using a program called smssend which has -update option, a cool feature which allows users to update the currently installed software. It's very reasonable to provide this feature since the software contains many scripts which may be updated at any time, and maintained by different persons. So a small but important change to any of the script doesn't require a new release of the software, but users can just run it with the -update option.

Update
I missed your point about using CVS behind the scene. If what left to users is just a submit button, then that will be fine. But using external programs or modules which depends on external programs/libs assumes the availability of the external things.