Cascade remove tries to delete child entities with wrong colum name for fk column

During testing our entities, I've found that a OneToMany relationship with `cascade={"persist", "remove"}` successfully persists child entities, but fails to remove them with a DBALException.

Parent Entity:
```class Scene implements CreateableInterface, SceneConnectable
{
use Creator;
use Deletor;
use SceneBasics;
/** @Id @Column(type="integer") @GeneratedValue */
private $id;
/**
* @OneToMany(targetEntity="SceneConnectionGroup", mappedBy="scene", cascade={"persist", "remove"})
*/
private $connectionGroups = null;
}
```

Child Entity:
```
class SceneConnectionGroup implements SceneConnectable
{
/**
* @Id
* @ManyToOne(targetEntity="Scene", inversedBy="outgoingConnections", cascade={"persist"})
* @JoinColumn(name="scene_id", referencedColumnName="id")
*/
private $scene;
/**
* @Id
* @Column(type="string")
*/
private $name;
}
```

Removal of the parent entity results in an exception:

```
Doctrine\DBAL\DBALException: An exception occurred while executing 'DELETE FROM scene_connection_groups WHERE scene = ? AND name = ?' with params [null, "lotgd\/module-village\/outside"]:
```

The issue lies in the naming of the fk column: Doctrine tries to use the colum name "scene", which does not exist in the table. Instead, the column is actually called scene_id as specified in `@JoinColumn`. Removal of the `@JoinColumn` does not change the result (it still throws the exception).

Renaming the join column to "scene" circumvents this issue. We use currently the most recent version (2.5.6) on PHP 7.1.

Start with the parent and child entity mappings in the issue, then reproduce the cascade remove operation on Doctrine ORM 2.5.6 with PHP 7.1 and inspect the generated DELETE statement. Done means the child delete uses the JoinColumn name `scene_id` rather than the property name `scene`, while preserving the composite-key behavior.

Written by the indexing model from the issue text.