#246 CMP2 set always marks field as dirty

[Jeremy Boynes]

Invoking a set accessor for a cmp-field will now always
result in that field being persisted. Previously fields
were only persisted if their value had changed (as
determined by equals()).

This ensures mutable values will be persisted if the
set accessor is called. Previously code such as
Hashtable temp = getStore();
temp.add(key, value);
setStore(temp);
silently failed to persist the new value.

This change may result in additional columns being
updated in scenarios such as when a bulk accessor
simply sets all members on a update operation,
resulting in a small performance degradation. This can
be avoided at the application level by explicitly
performing the equals() comparison (or better still,
not passing unchanged data into the EJB in the first
place).