I find it rather difficult to advise on this article and would suggest a different approach: Step back and describe the problem you're actually trying to solve. You seem to be stuck in "solution space", with some design decisions already made - but these might actually get in the way.

As an example, you write modules are intended as an abstraction of behaviours and scripts are generally the incarnation of these behaviours in the real life. I'd challenge that view and say that objects are the incarnations, and that you are (ab)using subclasses instead of different objects of the same class, each with their own attributes. Also, you seem to use scripts to store particular objects. All this might be justifiable, but I can't see how.

Also, the decision to be a fan of OO frameworks only when I will have the need to use all the features they provide seems questionable. You might fare better if you decide to embrace them as soon as they help to solve your problem. I am pretty sure that almost no one needs to use all the features of Perl itself, yet many of us are Perl fans, and quite happy with it.

So, perhaps the problem has occurred before. I don't recognize it. Chances are that some features of OO Perl frameworks have been created to solve your problem. Can you describe how you intend this to be used? Are users supposed to write their own modules, and how should they feed them to the system? Can you describe the problem without using the words "incarnation", "abstraction" and "design pattern"?