As you use Windows, I have seen such problems as Win use this port range for processes which use a 'random' port.
This behaviour is sporadic.
Other possibility is that you run another instance which is not correct stopped.
Does that happen if you start a fresh JBoss instance?
Do you have restared the system?
I restarted and it didn't fix it. But I was able to shut the service down which was occupying port 1098 and that allowed JBoss to deploy fully. It's good to know it's a sporadic issue caused by a random port assignment. I only have one instance of JBoss running. Thanks.