I think what you are trying to say is correct ( and for the record, yes, I'm aware of that problem), but you use the same incorrect words again in your new version, so let me try to change that with a few words:

If you're going to sell a perl application, and said application depends on includes CPAN modules not written by yourself, you *must* investigate the license(s) of those modules and if there are restrictions, either architect around the restrictions or negotiate a different license with the author(s)

Again, dependancy has nothing to do with it, it is merely packaging. No need to "architect around" anything, just don't put the modules into the tarball/CD you distribute and your work is done. This is an obvious approach anyway, since otherwise you never benefit from bugfixes to said CPAN modules (OTOH you also don't know for sure which version of the module the user has installed, but that's a feature as far as I'm concerned, because it requires you to keep your app up to date, which should result in fewer bugs).