cli batch incorrect handling of the enabled attribute during datasource creation

case:
/subsystem=datasources/data-source=xxxxxx:add(....) (without declaring enabled attribute)
the ds is created with enabled=true, consistent with xsd default, but after WFLY-86 shouldn't it default to false when omitted ?

/subsystem=datasources/data-source=xxxxxx:add(...., enabled=true)
the ds is created with enabled=true as requested

but in both cases the operation
/subsystem=datasources/data-source=xxxxxx:disable
WITHIN THE SAME BATCH is happily ignored, ie the final outcome is success but the state of the created ds is still enabled.

The opposite instead works, adding the ds with enabled=false produces a disabled ds and adding
/subsystem=datasources/data-source=xxxxxx:enable
within the same batch, produces an enabled ds.