Given the width of the Class::MethodMaker API I'd be surprised if any OO method generation was truly orthoganal to it! After all, the main purpose of your module is to provide a new() for sub-classes that performs certain convenient functions with respect to composition. That sounds a lot like the what many of the method makers in Class::MethodMaker do already.

However, I'm not meaning to suggest that having Class::Container as a separate module is bad. People may want to use it who have no need for the larger functionality of Class::MethodMaker.

As I understood your question, you asked if your new module fit anywhere in the existing OO landscape. I happen to think it does. Whether you choose to put it where I think it might fit is another question entirely.

-sam