Sandbox Bridge: questionable goals, questionable behavior

I have two application sandbox HTML windows that each contain IFRAMEs with content loaded from the same remote domain.  I'm trying to allow those IFRAME's contents to script between each other freely.

Pulling through the parentSandboxBridge and proxying to the other IFRAME's client seems to almost work, in that I can get some simple data through, however functions are stripped from return values.  Oddly, if I pass a function reference into the parent, request and call it from the other bridge that does work, but then the same data only limitations seem to apply on arguments and return values.  In any event, I suspect the entirety of what DID seem to work there might have been a bug in the sandbox intention considering the somewhat inconsistent ways it seems to work.

In searching for a different way to share a reference between these frames I stumbled on something interesting.  I'm wondering if Adobe would consider this a bug to be fixed or something that's not unreasonable to rely upon.

I create an app HTML window with HTMLLoader.createRootWindow and its HTML loads a remote IFRAME into it.  That remote content calls "window.name='x'";

Now I repeat the process with a new HTMLLoader.createRootWindow and remote IFRAMEcombo.  But this time the remote HTML calls "var orig = window.open('', 'x');" and successfully acquires a reference to the original child IFRAME, both in the correct domain, sandbox, and seemingly having my desired level of script access between them.

Did I stumble on something you'd like to FIX or is this a halfway decent plan for accomplishing my goal?

Thanks,

Andy Lippitt