Android 3.1 browser bug: Can get cached SSL certificates confused

I have seen this before, so figured I would document it with Android 3.1. The web browser can incorrectly apply cached SSL (HTTPS) certificates to the wrong web page, even trying to apply them to non-encrypted sites. In this most recent case it informed me that bitsum.com had an invalid certificate even though i was browsing in an unencrypted session. I checked the certificate and it was Facebook.com's, a site not even open in the browser.