A few people have reported this today. I think it is probably a conflict with eCart. We'll be looking into it and getting out a fix shortly.
The good news is, it appears you can just ignore that message and it won't cause any problems with any functionality for now.