JavaScript Module with Global Scope Removal
Even though I regularly rant about not including jQuery as a default, without ensuring that you actually need it, I have done so myself. However I have done it in a special way (at the time of writing, this is only a proof of concept, and not really used for anything...)
I have a global scope module called "clauswitt", that gets session.js and jQuery added through parameters to the module pattern. This module then removes session.js and jQuery from the global scope, thus making the jQuery code visible only from inside the module, and not callable from the outside.
UPDATE:
As Andrew Cobby pointed out in the comments (see below), you do not need to check if a global variable exists, before deleting it.
And just to clarify - this may not have a valid use case. The reason I created this, was because I got a question about wether it was possible, and how. (A friend of mine had a colleague who always created inline eventhandlers, using jQuery dollar notation directly in the onclick attribute of a button, for instance. This code forces him to - at least - create the code within the scope where jQuery is available).