Previously a NoSuchBeanDefintionException was thrown when the MethodSecurityExpressionHandler was defined in the parent context. This happened due to trying to work around ordering issues related to SEC-2136 This commit resolves this by not marking the MethodSecurityExpressionHandler bean as lazy unless it exists.