Not sure if that is as good of an idea - from the docs:
Due to the amount of uncertainty about the environment at the point
that load is invoked, you should avoid using load whenever possible.
Well, this is mitigated a lot for loadable bundles, though. There,
you're pretty much guaranteed that the app has already been loaded,
you just shouldn't use any other classes in your bundle yet. But
getting your own class object and adding it to an NSMutableArray in
the app itself is hunky-dory.
