Its just a question of ease of use for me. Without knowing how this affects day to day usage change is bad. The biggest problem with the current nesting of the maven2 repo being inside of the repository.jboss.com root is simply that its a little more difficult to separate I suppose. You can't just checkout repository.jboss.com to obtain one or the other of the repos. I would not change this until we have defined how one does a release to the repository using the mvn deploy target.
I don't think it would affect day to day usage, because we aren't changing anything about the existing repository.
The snapshot repo could be set up as a simple file server where developers can upload new snapshots as needed and/or automated builds are uploaded on a nightly or weekly basis. These files would not need to be in CVS or SVN. You wouldn't need to check out a copy of the repository locally because maven "deploy" can be configured to copy the file to the server via ftp or through a share or one of a few other ways.
The current /maven2 repository would be only for releases. That might keep it a little cleaner than if the two are combined. Eventually we could have the release engineering team responsible for doing releases, and take away developer access to the releases repository.