Maybe I'm underestimating Twitters developers, but in this case I honestly doubt Twitter had a QA process testing if things remained in browser cache at all, until someone pointed out that there is a problem. If they had thought about it as a problem, adding the cache header would have been easier to implement and test for than browser testing somehow.