To be honest I never experianced this with ESX 4, and thats what a bug is, its a bug some people get affected with it, others dont.
The KB you references only covers ESX not ESXi so I would say its not or has not yet been reported as an issue with ESXi.
I personally havent seen it in the hundreds of ESXi 5 servers I look after