I don't see anything wrong with it. To some extent, it may depend on who is claiming the copyright. If you, personally, are taking the copyright and making it open source, and your $WORK is licensing it to use it, then release it under your author ID. If $WORK is keeping the copyright, then maybe release it under a $work ID to help make that distinct from any other work you release on your own.
I'd think about adding your personal ID as a 'co-maintainer'. And you'd want to make sure that the XXXX at cpan.org email forwarding goes somewhere that won't disappear if you leave the company.
Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.