I imagine this is inconsequential, but we haven't reproduced it locally yet and are still very interested in getting it resolved. We may have to work directly with someone having this issue in order to track it down. I'm thinking it may be a conflict with the eCart code. I'll see if I can reproduce it Monday morning by installing eCart... we may have to release a compatibility fix for eCart to prevent this error.