I can confirm that the bug you are seeing is only in SW2003 SP5. It is correct in SW2003 SP4, and SW2004 SP0 and SP1.
I came across the bug the first day after I installed SP5.0. I submitted the report to my VAR, and was told that they believe that SP5.0 will be the last SP for SW2003.
Also...