I'm not sure why you would think that? The issue described in this blog post is relating to the performance of a particular CSS selector that jQuery implements - not really anything having to do with memory usage (and the memory usage of jQuery certainly isn't anything significantly above-and-beyond what a normal web application would use).