2011-06-26 (1:26P EST) You may be looking for a deep copy of your framework
Since you haven't provided an example, here is one using jQuery. For each new "instance" you would add a property to frameworks, which would hold it. Or you could just use a frameworks array and keep pushing your instances onto the stack. Either way, it will be one variable to hold the multiple instances/copies.
var frameworks = {};
frameworks.a = jQuery.extend(true, {}, jQuery);
frameworks.b = jQuery.extend(true, {}, jQuery);
(function($){$.fn.foo = function(arg){var foo=arg;}})(frameworks.a);
console.log(frameworks.a.fn.foo.toString()); // uses 'arg'
(function($){$.fn.foo = function(bar){var foo=bar;}})(frameworks.b);
console.log((frameworks.a).fn.foo.toString()); // still uses 'arg'
Original Answer
Is this something that you're after?
var frameworks = {};
frameworks.base = function(i){var foo = i; return foo;};
frameworks.a = (frameworks.base)('a');
frameworks.b = (frameworks.base)('b');
document.write(frameworks.a);
document.write(frameworks.b);
Author's Comment
: I guess 99.99% of people just use frameworks and don't build their own so if you don't know don't try to answer something you do not understand yourself :)
Response
: I guess 99.99% of the people that do build their own, don't come across something like this, because they understand the purpose of a framework and that if you need instances of one, you have a design flaw. Additionally, if someone was so "well equipped" to design a framework that doesn't already exist in the www, then they should be able to understand how to implement their own "instances" w/o convoluting the global namespace.