Straight connection overloading. We're already redirecting the majority of the files - but somehow the hotlking continue to persist.
Makes sense, good decision then.
How are you preventing hotlinking while still allowing the files to function normally on jquery.com? Inspecting the referrer or checking to see if other resources were previously downloaded?
You can do it in your .htaccess file. Define some extensions that are blacklisted and redirect referrers outside your own domain to a place of your choice.
CPanel allows you to do this directly (although you might want to back up your .htaccess file first).
They are not disabling their CDN. They are only disabling hotlinking against other sources. This was in the first sentence.
I understand that. The question still stands - if it's a bandwidth problem on jquery.com, why not just 301 it somewhere else?
Because 301'ing provides little or no incentive for the offenders to do the right thing. Also it doesn't stop the excess traffic, it just reduces it.