IndexedDB versionchange transaction seems to persist across page loads

[Aaron Shafovaloff]

In both Chrome 26 and 29 (Canary). To reproduce:

```javascript

var request = window.indexedDB.open('acme');

var request = window.indexedDB.open('acme',2);

```

Even across page reloads, etc., the hanging versionchange transaction seems to persist. One can no longer successfully open the database, i.e. window.indexedDB.open('acme'); 

Only restarting the browser seems to fix this. It seems I can only do a successful versionchange if I *initially* open the database with the new version number and onupgradeneeded event. If I try to open it with an unspecified version, "inspect" the existing database structure, close it, and then open it again with an increased version number, then I'm stuck with a pending versionchange transaction and I have to restart the browser.

Please give IndexedDB some love.

- Aaron