please post to CMP user forum.
This is a legitimate EJB 3 issue. This appears to be a shortcoming of the EJB 2.1 design and implementation, and it is reasonable to ask that it be addressed in EJB 3.
Will EJB 3 address compound primary keys with split foreign key relationships?
Is my description of the table design pattern adequate, and do you understand the pk/fk design I'm referring to? I don't think the EJB specification has been tested against enough real-world database models.