In addition, it is important to note that this standard does not address some other areas that may be important to enterprises. 802.11e does not provide Quality of Service on a per application basis. This means that if a laptop is simultaneously running a soft phone for a wireless VoIP call as well as checking email, the device receives the high priority assigned to it, not just the voice application. This situation worsens contention.
Also, 802.11e does not solve the problem of collisions being caused by neighboring cells, or co-channel interference. A call could have priority in the cell that it is communicating in but with only three channels available in 802.11b/g (which is what phones run on) there will inevitably be overlapping traffic from other cells which will further increase contention for that client. So the contention problem is not how many clients attached to that single AP but how many clients within "hearing range" of each other on the same channel.
Lastly is the inter-AP handoff problem. Today most WLAN systems (though not all) do not manage client handoffs during roaming. The roaming handshake is initiated and controlled by the client. The process of handing off as you roam can take anywhere from 200 - 300ms. This can destroy a VoIP call that can't tolerate more than 20 to 30ms handoffs.
So in a small environment where inter-AP roaming and co-channel interference aren't an issue 802.11e will help a great deal. In larger environments if you're relying on 802.11e as your sole QoS mechanism you'll be pretty disappointed as more users get on the Wi-Fi network.