That would involve creating 2.3-modified jars, syncing to the 2.4 release, and running API Checker, just to update a file that is no longer used. I'll leave it for the next guy to worry about.
It's convenient to have the history of conf files when creating a new config file, even if they aren't exactly correct. Rajeev is right that we could delete them, but its not as if they take up any space. I say leave it as is. http://gwt-code-reviews.appspot.com/1721803/ -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
