Yes I had one of those errors logged too, but it happened on the same day as release so I was unable to determine if it came from the release or test code. The plugin will still work fine. We simply tried to unhook the events before the plugin unloads, but this happens automatically anyway.
I think the next release will mostly have a little bit of code cleanup and remove those unhook events. Thanks for the report.