This wouldn't bother me so much if it wasn't also incredibly inefficient relative to procedural Perl. Of course object-oriented design will always have more overhead, but it shouldn't have that much more. As for performance relative to procedural Perl code, I'm thinking something along the lines of Objective C's efficiency vs. plain C. Objective C is nearly as dynamic as Perl and doesn't give up too much to plain C in terms of execution speed. I don't think pseudohashes and such go far enough. But this is not all bad.
Decisions have to be made and syntax has to be created.
There will still be plenty of Ways to Do It, in my opinion. The old procedural model should remain, of course. And I'm not saying that every one of Perl's internal functions and operators should be replaced with object-oriented variants. All I'm asking for is a better world for object-oriented Perl programmers. And I think it's something that everyone can agree on, since there's a lot of benefit to be had, and no down-side that I can see.