Firefox doesn't support it, which I think is rather disappointing. The feature request has been around since 1999. Good SRV record support across browsers would assist with many other issues too.
In the case of Jabber/XMPP it seems to be universally supported by servers now. Most clients should support it as well. Both are required to support it to be XMPP (RFC 6120/6121) compliant, possibly because there was no standard privileged port that could be allocated.
Or phrased differently, what's the disadvantage of pointing your main domain to the www server?
At least with SRV records, a framework is available for routing based on context. But without them, it doesn't necessarily make sense to establish a default. In a web-centric environment with a single public facing site with low traffic, it might be useful to assign the top level domain an IP address. In more complex environments, it could create as many or more problems than it solves.
Sure, email is like this thanks to MX records. We could have the same for web servers by using SRV records ("_http._tcp.example.net" pointing at your "real" web server[s]) but I have no idea how many browsers support looking up SRV before A.