However, even though I've come quite far in Perl, I have yet to pursue Object Oriented Perl.

I find that a strange sentence. I wouldn't claim to be quite far in Perl without having done any OOP. That's like saying "I'm quite far with learning how to drive, I've yet to make a left turn".

So, my question is this...*finally, you say*...should I stop where I am, and come back to learn object orientation in Perl?

Well, you could do two things. Either learn OO programming in Perl first, so you'll just accept how things are. Or you first learn OO programming in a language that does OO halfway decent (like Java, even if they don't do MI), then turn back to Perl and think "WTF was Larry thinking" for the rest of your life. I did the latter, and after 15+ years, I still loathe OO programming in Perl.

Is it more a concept to learn, than something to do with a particular language (other than syntax, of course)?

For most languages, it's more a concept of learn, with some syntax attached. In Perl, it's like getting a lump of metal, some rubber, and a dozen manuals on how to create your own bike, with hundreds of fanboy cheering that this allows you to create whatever bike you want. (The same fanboys will dislike C for its low-levelness, even if it gives you all the tools to write a much better regular expression engine that Perl has...)

Am I leaving my Perl quest immaturely if I've skipped object oriented Perl?

Yes. Regardless of ones opinions of OOP, it's important.