gazouteast, man ... You're misunderstanding what WordPress, or ANY web app, does.
WPMS 3.0.1 has completely banjaxed the mail-based subdomains (hosts) set in DNS and made them inaccessible.
WordPress does not have the ability to redirect wildcard subdomains. It has the ability to interpret any wildcards that are set to it.
Your SERVER setup says 'Any time *.domain.com comes in, send it to /public_html/'
WordPress says 'Hey, I got a request for jimbo.domain.com!'
Your SERVER is what says to pass the data to WordPress or not. WordPress has ZERO control over that.
Basic laws of servers.
What is the BIG change in WPMS compared to WPMU? The one that leaps out at me is that for some reason Automattic deprecated the WPMU VHOSTS function in favour of is_multisite() in the wp-config.php settings - I am certain it is related to that now.
There is no VHOST funtion. There is a VHOST constant
VHOST = virtual hosts, aka ServerAlias, aka PARSING Wildcard DNS
If "no" blog urls look like http://mysite.tld/blog1 aka "sub-directories". If "yes" blog urls look like http://blog1.mysite.tld aka "sub-domains"
So ... that's exactly what is_multisite() parses. And by the way, it's not is_multisite() in the wp-config, it's a CONSTANT.
define( 'SUBDOMAIN_INSTALL', true );
Much easier to understand for most of us, I think :)
Look, I'm not saying you're wrong, but you're running down a path that is premature at best, and certainly a fair game at over-reacting.
The number of people having this problem are VERY few. A handful on the forums (out of the probably 100k people using MultiSite). Occam's Razor being what it is, the problem is most likely in how you configured your server to parse wildcard domains.
This works for a LOT of people. Windows and *nix, cPanel and Plesk, etc etc.
If you REALLY think this is a BUG in WordPress, don't be a dink and threaten with a Press Release. Man up and do the right thing by the open community. Open a Bug report. List the details of your server info, provide your http.conf (or whatever you have) so people can see what it's set up as. If you're using brad1004's fix (renaming the vhost files so they are called before each other), list what yours are, complete with each file's content.
But a theeat, man? That doesn't help anyone, least of all you.