[WFLY-1845] Upgrade HornetQ to 2.4.0.Beta1

* upgrade HornetQ to 2.4.0.Beta1
* use a pooled connection-factory as Java EE's default JMS connection
  factory
* do not enlist the XA resource in JMSContextProducer when a transaction
  is active, HornetQ's XA connection is taking care of it
[WFLY-1287] Provide JMS Default ConnectionFactory

* use java:jboss/DefaultJMSConnectionFactory binding to provide the default JMS
connection factory to deployments
* simplify the destination injection
[WFLY-1337] JMS Destination definitions

simplify code
[WFLY-1337] Support JMSConnectionFactoryDefinition

* parse deployment descriptor and annotations for JMS connection factory
  definitions and create manageable pooled connection factory for each
  definition
* add a createBinderService boolean to ResourceAdapterActivatorService
  to be able to prevent it from creating a binder service. When a JMS
  connection factory is defined by annotations or DD, the
  BinderService is already created before calling the
  DirectJMSConnectionFactoryInjectionSource.getResourceValue() method