Oddness around rollbacks and after_commit callbacks

During an aasm transition (before or after), I'm storing an array of values in a virtual attribute. If the commit of the instance is successful, I want to trigger an event using that array. If the commit fails (rollback), I don't want that event to trigger and I need to reset the array to nil.

I save instances in two ways using aasm:
customer.close!
and
customer.close
customer.save

By using aasm to save the instance (with the !), if there is a validation error (not having to do with the transition), the after_commit callback gets called no matter what and just says "false" and after_rollback doesn't get called.

On the other hand, if I do the second method of saving by using .save, the behavior is different and does trigger after_rollback.

Lastly, let's say the instance is invalid and I save it through aasm like so: customer.close!. It'll return false for the save but still trigger after_commit callback on rails, which seems really odd.

Am I doing something wrong or is this a bug?

I wrote a stackoverflow question about it as well: http://stackoverflow.com/questions/39381484/after-commit-not-working-as-expected

Start by reproducing the two entry points described: customer.close! versus customer.close followed by customer.save, with an invalid instance and the virtual array attribute. Trace the after_commit and after_rollback callbacks involved in each path. Done means the callback behavior and array reset are consistent with whether the save commits or rolls back.