I did some looking into this and that is simply how MS has it set to be in the OS.
One user was able to remove it by doing some interesting hacks in the event log to get it to be removed completely from it. But other than that it isnt a bug that can be fixed as it is the way MS wrote the event and they have never fixed it.
As an example, if I am writing to the event log I tell it the message give it an ID and tell it if it is a warning, error or information. In this case the service is passing the wrong type to it, so it shows as a warning instead of information.
Shane