I doubt that you can (or necessarily should) convince your colleagues to give up their unpaid hours to learning perl to benefit the company, though it might be possible you could convince some to do so to benefit themselves - for the sake of having perl on their resume, or just to become a more effective programmer, or for the fun of it. But the people who would be swayed by such arguments would likely already be twisting your arm for a study group.

Talking to management is probably not the best first step (though this depends on the company), since it may result in management imposing your suggestions on reluctant colleagues, who are unlikely to thank you for it.

So I'd start by talking to your colleagues: do they see the lack of peer review of your code as a problem? Would they be happy to learn perl by going on a course? Would they be happy to learn from you inside work hours? Having learnt perl, could they imagine using it in the future, in another job? The answers to questions such as these would help clarify what to suggest to the management, or may convince you that you should do nothing.

Another approach is to teach by stealth: if you ever do code walkthroughs, try walking through some examples of your perl code, pointing out bugs and explaining how to fix them, and just describing what the language is doing as you go.

Good luck. :)