Yes, this is a bug in JBoss 3.2.2. The bug was not present in JBoss 3.2.2.RC4. It will be fixed in the next release. Meanwhile, there is an easy workaround: pass the server the "--host=<my-ip-addr-or-hostname>" command line argument to set the host address. E.g.:
run.sh -c all --host=my.host.name
run.sh -c all --host=xxx.xxx.xxx.xxx
Without the "--host" argument, JBoss 3.2.2 will use 0.0.0.0 (which is not a valid endpoint) as the host address.