[AC-2764] Event fired from addEventListener breaks CommonJS Monkey Patch

I am using CommonJS modules in my app, along with a "Monkey Patch" similar to this Gist: https://gist.github.com/1207520. The Monkey Patch ensures that require()d modules are only interpreted once -- after the first require(), subsequent require()s pulls the module out of the scriptRegistry cache. I've made a minor change to the Monkey Patch script to NOT "root" the module if there is an export of the same name, as well as add some debug logging. No other changes are made. The changes I've made are below. The issue that I'm having is as follows: 1) In app.js, the first thing I do is Monkey Patch the current script context. 2) Next, I create a window, and add an event handler for the 'focus' event. 3) In the 'focus' event handler, I require(test2), which goes to the Monkey Patch. Since this is the first time the module test2 is required, Monkey Patch forwards it to the real require(), and the module test2 is interpreted. 4) Next, I require(test1). Again, this is the first time test1 is required, so it is interpreted. 5) However, in test1, I require(test2). This require() call does NOT go to the Monkey Patch -- the "real" require() is called, and my Monkey Patch is never called. This is the bug. All modules require()d in test1 (and sub-modules, etc) are NOT Monkey Patched. This causes performance problems, as most of the require() calls in my modules are not passed through the Monkey Patch handler. I can only repro this issue when the require(test2)/require(test1) sequence are called in the 'focus' and similar event handler. If these calls are placed in the app.js context, everything works ok -- the require()s in test1 are patched properly. Other event handlers for the window, such as 'open' also appear to repro this problem. Here's a reduced repro:

// monkey patch first
require('requirePatch').monkeyPatch(this);

// create a window
var win1 = Ti.UI.createWindow();

// hook the focus event of the window to know when we should create our view
win1.addEventListener('focus', function(e){
    Ti.API.info("win1 focus event");     

    // Load test2, the first time this is attemped.
    // The monkeyPatch works, require()s it, and saves it in the script registry.
    // TEST2 should be printed once at this point, and this is the only time it should be printed.
    Ti.API.info("win1 focus event: SHOULD print TEST2:");  
    require('test2');
    Ti.API.info("win1 focus event: (SHOULD have printed TEST2)");
    
    // Load test1, which also loads test2.  At this point, for some reason, 
    // running the context inside test1, require won't be monkey patched.
    // This is where the problem occurs: TEST2 should *not* be printed again, but is.
    // None of the modules loaded under test1 will have monkeyPatch working.
    require('test1');
});

// create tabs to show 
var tabGroup = Ti.UI.createTabGroup();
tabGroup.addTab(Ti.UI.createTab({
    window: win1
}));
tabGroup.open();

Ti.API.info("TEST1");

// THE BUG: For some reason, require isn't monkey patched any more.
// TEST2 will be printed again as test2 is re-interpreted at this point.
Ti.API.info("TEST1: SHOULD NOT print TEST2:");  
require('test2'); 
Ti.API.info("TEST1: (SHOULD NOT have printed TEST2)");

Ti.API.info("TEST2");

exports.monkeyPatch = function(object) {
    Ti.API.info('requirePatch.monkeyPatch()');
    
    var scriptRegistry = {};
    var oldRequire = object.require;

    if(object && !object.monkeyPatchRequire) {
        
        Ti.API.info('requirePatch.monkeyPatch(): Installing');
        
        object.require = function(moduleName) {
            
            Ti.API.info('requirePatch.monkeyPatch().require(): ' + moduleName + ' ' + (scriptRegistry[moduleName] ? 'HIT' : 'MISS'));
            
            if(!scriptRegistry[moduleName]) {
                var mod = oldRequire(moduleName);
                scriptRegistry[moduleName] = mod;
            }

            return scriptRegistry[moduleName];
        };

        object.monkeyPatchRequire = true;
    }
};

Here's the output from running this: {noformat} I/TiAPI ( 5665): (kroll$1: app://app.js) [12,731] requirePatch.monkeyPatch() I/TiAPI ( 5665): (kroll$1: app://app.js) [5,736] requirePatch.monkeyPatch(): Installing I/TiAPI ( 5665): (kroll$2: file:///android_asset/Resources/app.js) [74,507] win1 focus event I/TiAPI ( 5665): (kroll$2: file:///android_asset/Resources/app.js) [4,511] win1 focus event: SHOULD print TEST2: I/TiAPI ( 5665): (kroll$2: file:///android_asset/Resources/app.js) [3,514] requirePatch.monkeyPatch().require(): test2 MISS I/TiAPI ( 5665): (kroll$2: file:///android_asset/Resources/app.js) [18,656] TEST2 I/TiAPI ( 5665): (kroll$2: file:///android_asset/Resources/app.js) [5,661] win1 focus event: (SHOULD have printed TEST2) I/TiAPI ( 5665): (kroll$2: file:///android_asset/Resources/app.js) [22,683] requirePatch.monkeyPatch().require(): test1 MISS I/TiAPI ( 5665): (kroll$2: file:///android_asset/Resources/app.js) [33,925] TEST1 I/TiAPI ( 5665): (kroll$2: file:///android_asset/Resources/app.js) [7,932] TEST1: SHOULD NOT print TEST2: I/TiAPI ( 5665): (kroll$2: file:///android_asset/Resources/app.js) [6,994] TEST2 I/TiAPI ( 5665): (kroll$2: file:///android_asset/Resources/app.js) [22,1016] TEST1: (SHOULD NOT have printed TEST2) {noformat} The second-to-last line of output should NOT be "TEST2", which means that the module "test2.js" was re-interpreted.