Since your $moduleRef object is not the same as your actual application object, chances are that they will each create their own session (and configuration, and do all kinds of other stuff you'd really only want to do once).

In general, basic CGI::Application systems only have one controller (i.e. one instance of a CGI::Application-derived object).

Is there any reason you don't run the myTest::module1 as the application's class instead of creating a new instance of it somewhere during a handler?