The default idea is that individuals do the work so that's who the CPAN account should belong to.
(plural) do the work, so that's who the CPAN account (singular) should belong to.
Seems like a pretty good definition of an organizational CPAN account to me! ;-)
Having said that, there are some difficulties. If I were to work at $ORG which releases a package $PACK on CPAN, using account $NAME (be it a personal or a organizational account), with $NAME comes password $PASS. Now I stop working for $ORG. I probably shouldn't have write access to $PACK anymore. But that would require changing $PASS, and distributing passwords. It's even worse if $PACK was distributed on my personal CPAN account. Then maintainership of $PACK would need to be passed, and if me parting with the company was not on friendly terms, I might not want to cooperate.