I mentioned 3 potential issues with multiple perls on windows. BTW the same issues exist on Linux as well the difference is that on Linux the users are usually more aware of the PATH end the PERL5LIB env variables and are usually not using file extension association to run their scripts. (and sh-bang has its own issue)

Constantly renaming the directories as you suggested is a solution but it means you cannot use both of them at the same time so you cannot run Padre on Strawberry while at the same time running your scripts on ActivePerl.

The new StandAlone Padre installation will solve this issue as it will basically hide the face from the world that it is using perl. It won't add its bin directory to the bath and it will have a (probably .bat) launcher for Padre so the .pl file association will be also irrelevant to it.

It is planned to be ready in a few months from now but with some help we might be able to move it earlier.