Answer
No — this is a routine, non-error informational log entry generated whenever the middleware normally recycles or closes an existing pooled database connection as part of its regular connection-pool management; it's logged at Info severity precisely because it's expected routine behavior, not an error condition. A genuine underlying connection-pool problem would instead manifest as users being unable to log in at all — as long as logins are working normally, this specific Info-level log message on its own isn't something to be concerned about.