Added tests to Scheduling project.

This is cheating. :)

You're sprinkling test related calls in your 'main' code just to test it.

Rather use CDI features to override the MySingletonEJB for test purposes, e.g.:

```java
@Alternative
public class TestMySingleTonEJB extends MySingletonEJB {
  public static CountDownLatch timerScheduleCountDownLatch = new CountDownLatch(3);
  
  public void myJob() {
    super.myJob();
    timerScheduleCountDownLatch.countDown();
  }
}
``` 

Then in the @Deployment add a beans.xml that activate this Alternative bean. Not sure how the @Schedule is read in this case, if super class is read or not, but anyway it might be a good place to set a new 'test' schedule time as well.

See complete example of the 'Alternative way' here; https://github.com/arquillian/arquillian-showcase/blob/master/cdi-ejb/src/test/java/com/acme/cdiejb/async/FireAndForgetUsingAlternativeBeanTestCase.java