A better way to program is with interfaces and composition via delegation, something that Java and C++ support but have no syntax for making it easy. Perl's Moose object system, on the other hand, has easy support for composition via roles and delegation via ... well, delegation :)
And, you have "extends"-style OO available if you think it's the right solution to a particular problem. So really, I think it's a fine way to learn OO. Doing things right is easier, if you decide to do them right.
(We do Java OO right at Google, but it sure involves a lot of typing and @hacky-attributes. And I've never seen good Java OO anywhere else.)
I have used Java and Python extensively now and I like Perl a lot more. All three are quite usable, however.
And I do want to remind readers that Moose is not the Perl object system, it's an object system added on top of the mess that a huge collection of legacy code presumes.
After learning Moose a couple of years ago, I don't miss the Perl 5 mechanism at all.
My first programming job was in Perl back in the late 90's. Loved it, but I have to say that the OO facilities left something to be desired. I found them fatiguing. It took Java, then Smalltalk for me to really get OO. Perl requires too much mastery of mechanism just to do objects, so it's not the best environment for learning OO.