Perl has the great advantage that its OO features are flexible and not mandatory.
A language, like Java, that is built around OO must be built around some particular theory of OO. The result is that, in use, your classes must be built to meet the constraints imposed by the language. OO language bigots have immense flamewars over whose OO flavor is purest. The languages they all love to hate are Perl and C++, for leaving the rules up to the developer.
I've been told (by merlyn ;-)) that the book you mention is ideal for your purposes, and that TheDamian's Object Oriented Perl makes the perfect follow-on study.