@Zeus - we're using the new Web Audio API in Chrome which no other tools are doing yet. Chrome tends to crash and have memory leaks with HTML5 audio, and HTML5 audio has extremely limited features, so we switched to the new (and much better if this bug didn't happen) Web Audio API. Chrome's Web Audio API has this bug so it's in the browser, and that explains why other tools don't have the bug (they don't use it yet), but there's still nothing we can do about it. Usually they have quick fixes though, Chrome gets updated every 6 weeks ish, so hopefully it won't be around for long and will just get fixed.
We can't really go back to HTML5 audio or Chrome will start crashing and leaking memory again :-\