My duty to purge caches if uninstalling plugins with JS/CSS references in pages?

Scenario:

• T0: Plugin-X in use. Embeds its JS/CSS file(s) via <script> in all pages with src pointing to JS/CSS files inside its plugin folder.
• T1: Page-A (among others) cached with JS/CSS resource references to Plugin-X folder in page markup.
• T2: Plugin-X uninstalled, hence also its folder deleted.
• T3: Page-A requested with cache-validation still serves the cached version from T1. Resulting in 404s because the JS/CSS file(s) were in the plugin folder which meanwhile got deleted.

In such a situation: Who is responsible to purge pages with references to JS/CSS resources coming from plugins meanwhile uninstalled?

1) Plugin X needs to trigger a certain mechanism?
2) WordPress?
3) W3TC? Which should detect that plugin X got uninstalled and thereby all pages which embed plugin X JS/CSS files need to get purged?
4) Or is there currently no architecture for this? And hence the admin’s responsibility to purge the entire cache after uninstalling a plugin which is known to put JS/CSS resource references into the markup of cached pages?