Hi,
what do you mean by "content cache"?, as far I remember there is no content-cache feature.
The only automatic cache EAV features is for holding the list of virtual columns of each table, but this is properly handled when adding or removing virtual properties. Also remember that Contents do not use EAV directly, they use the Field API which, yes, is built on top of EAV API.