Most folks probably write JavaScript for the browser.
Not only should you consider using object pooling for JS objects (like the author describes), but you also want to think about DOM element pooling, especially when you are dealing with large lists.
DOM element reference cacheing (and pooling) can significantly improve the responsiveness of very busy browser UI code (particularly in loops that make many DOM queries and/or updates) and can make the code more readable too, but be careful as you can create memory leaks especially in "classic" IE. Such leaks only tend to last as long as until the user navigates away, but they can become significant for single-page applications.
Not only should you consider using object pooling for JS objects (like the author describes), but you also want to think about DOM element pooling, especially when you are dealing with large lists.