Hi Dana, Ben.
When that log entry was implemented, the plug-in was being refactored, and it was useful for troubleshooting regressions or bugs.
Now I agree with you two, so let's fix it.
The reason why, even though the script works, the message is still displayed; is that - from what I recall - there was one initial call done, before the screen was completely rendered, and that generated this log entry. Shortly after that there is another call and the message should not be displayed again (though it may be happening anyway).
The fix is quite simple. Let's make this a debug level entry only, and prevent it from spamming the logs. Included in the next release (as soon as I find some spare time for that).