I don't think that that's a problem - but instead an advantage.

At the moment the charmworld search results create separate models for all 'entities' and then we make extra requests elsewhere to grab the same data for the charm details page and to deploy the charm. We should be storing all of these in the database instead so that we don't have to make these requests.

So at the moment the cache will be storing these superfluous models but once the above work has been completed this this will allow an easy switch over to reduce the duplication in memory.