ID 226414 - Image sources duplicate when upgrading a project from 2.x to 3.x

Problem summary
When taking old projects from 2.0 to 3.0 with images in the image manager that are plugged into layers such as a Tiled Procedural and that said layer is not the layer the project is saved in 2.0 with as current then the image is duplicated and proceeds to stay in sRGB and eventually disconnects leaving a black image remaining. Please see images below for a clearer illustration of the issue.

Figure 1) The project as seen in 2.6 (note: the project was not saved in this state, but on a different channel)

Figure 2) The project when imported into 3.0v4, there are two images for one procedural in the Image Manager

Figure 3) When cycling off 'Raw Data' on the duplicated image, graphical errors appear and the image fails to be presented on screen.

Customer reported version

3.0v4

Customer reported platform
n_a_linux

Steps to reproduce

1) Take any geometry, e.g. the example head project and launch Mari 2.6v5
2) Create two channels 'A' and 'B' 
3) On Channel 'A' create a Tiled Procedural Layer by going to Layer>Add Procedural Layer> Procedural> Tiled
4) Add any image to this tiled procedural. 5) Select Channel 'B' then save and exit the program.
6) Launch Mari 3.0v4. Load the project, convert the layer data when prompted.
7) Select layer 'A' and observe the change in colour based on our 2.6v5 project, as well as the duplicated images.

8) Also unchecking 'Raw Data' on the image managed image will eventually break the image, resulting in a black object.

Reproduced by support
Repro'd on Centos 6.2 and Windows 7. 
3.0v2, 3.0v3 & 3.0v4 

Expected behaviour

The image to come in without a duplicate, for it to be set to 'raw' and not to break when cycled between raw and sRGB