Bug 1134278

Description of problem:
- It has been observed that Boundary Event associated to a User Task is listening for the signal even when the User Task is not active. To prove this behavior I have attached a sample jBPM6 Project which can be imported in JBDS or any Eclipse based IDE and execute the "ProcessMain.java" class to reproduce the problem.
- I have a process which has the following sequence of flows.
~~~
Start -> Signal -> XOR gateway (Converging) -> Script Task -> User task 
(having a Boundary Event) -> End

 User task (having a Boundary Event) -> XOR gateway (Converging) -> Script Task -> User task (having a Boundary Event) -> End
~~~
As it can be seen from above flows there are two signal events and they both use the same SignalRef "SignalOne" , and when the process is instantiated it waits for signal to continue moving forward. Now, the problem is that when the process instance is signalled , it is observed that the script task is executed 
twice. Note that the Boundary Event attached to the User Task redirects 
the process flow the the XOR gateway again when it is signalled.
- Ideally, a boundary event should only be active when the node (it is attached
to) is active. Hence, it appears to be a buggy behavior.

Version-Release number of selected component (if applicable):
- BPMS 6.0.2

How reproducible:
- Use the attached "BuggySignallingOnBoundaryEvent.zip" JBDS project to reproduce the issue.

Steps to Reproduce:
1. Import the attached "BuggySignallingOnBoundaryEvent.zip" project in JBDS or any Eclipse based IDE and try to resolve the dependencies if required.
2. The process definition should already be packaged in the Jar "jbpm-example-1.0.0-20140827.062224-2.jar" which has been included in the Build Path. So, just go ahead and execute the "ProcessMain.java" class to reproduce the problem.

Actual results:
- It should print the SYSOUT statement from the script task twice like this. Which should not happen. 
~~~
######### STARTING PROCESS INSTANCE #########
######### PROCESS STARTED NOW SIGNALLING IT #########
This script has been FIRED from the 'STask1' Script Task... 
This script has been FIRED from the 'STask1' Script Task... 
######### PROCESS HAS BEEN SIGNALED #########

~~~

It is happening because the Boundary Event attached to the User Task is also listening to the same Signal which is being listened by the first Intermediate Signal Event in the process definition. That is the reason why the process flow moves again into the XOR gateway from the User Task and the Script Task is again executed.


Expected results:
- The Boundary Event attached to the User Task should not be listening to the Event at this moment.

Additional info:
- Not Applicable.