Using EJB2.x / XDocled I have to insert <cascade-delete/> tag on "many" side and it seems very natural for unidirectional ManyToOne relationships - "one" side remains clean, without declared collections that are never used.

But EJB3 forces to create stuppid and useless collection on "one" side, forcing creating bidirectional relationships if I have to cascade removing - I have to add @OneToMane(cascade=CascadeType.REMOVE) annotations on "one" side.

Is there any way to remain the relationship unidirectional when I only need cascade removing corresponding "many" side entities?

Of course EJB3 does not force you to define a bidirectional repationship