cq:includeClientLib in a component that might be part of a teaser I'm having some challenges around clientlibs and personalization. It seems like one of the real strong benefits of the clientlib concept is the ability to put a cq:includeClientLib tag on a component, and let AEM manage only including it on the page once. However, this breaks down when using the personalization functionality, where HTML fragments are loaded via Ajax.As an example, I tried this with the Adaptive Image component. I created a page with a parsys. I dragged an adaptive image onto the parsys and set an image for it, then I dragged a teaser onto the parsys, and set the campaign and strategy. The campaign had a single offer page, which had an adaptive image on it. When I loaded the page, I could see that the cq:includeClientLib in the adaptive image's JSP was causing some libraries to be loaded twice, and causing some to initialize twice, so that in the final state the page actually displayed three images instead of the two that it should have.As we're thinking through the com